Split-brain, named by analogy with the medical Split-brain syndrome, occurs when two parts of a computer cluster are disconnected, each part believing that the other is no longer running.
High-availability clusters usually use a heartbeat private network connection which is used to monitor the health and status of each node in the cluster. One subtle, but serious condition every clustering software must be able to handle is split-brain.
Split-brain occurs when all of the private links go down simultaneously, but the cluster nodes are still running.
If that happens, each node in the cluster may mistakenly decide that every other node has gone down and attempt to start services that other nodes are still running. Having duplicate instances of services may cause data corruption on the shared storage.
This problem can lead to data inconsistency. To prevent it computers should use redundant communications and fall down to an auto-fencing mode when the peers look like they are down. This means they should run in a limited mode to prevent data destruction